-
-
Notifications
You must be signed in to change notification settings - Fork 218
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add entry to subevent log when filtering out recipient #35509
Conversation
🔍 Existing Issues For ReviewYour pull request is modifying functions with the following pre-existing issues: 📄 File: corehq/messaging/scheduling/scheduling_partitioned/models.py
Did you find this useful? React with a 👍 or 👎 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
minor comments
@@ -344,7 +344,7 @@ def log_filtered_recipient(filtered_recipient, reason): | |||
filtered_recipient, | |||
content, | |||
) | |||
sub_event.error(MessagingEvent.FILTER_MISMATCH, reason) | |||
sub_event.error(MessagingEvent.FILTER_MISMATCH, reason, MessagingEvent.STATUS_COMPLETED) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
that makes sense to do
Product Description
When alert recipients are filtered out it is hard to figure out why. Currently we have bug in production that we cannot reproduce otherwise. This will help determine what exactly is happening.
Technical Summary
https://dimagi.atlassian.net/browse/SUPPORT-22779
Feature Flag
None
Safety Assurance
Automated tests and tested on staging.
Safety story
Automated test coverage
Yes.
QA Plan
Rollback instructions
Labels & Review